So, you’re looking to build a web site or so fed up with your current web host that you are desperate to transfer your site elsewhere? You may not even be aware of your current host’s vulnerabilities in an industry where each week there is news about a host going down for one reason or another. Your first problem is narrowing the thousands of choices down to a few that you can research further. Seek friends or associates that have a web site and ask for their advice. Visit one of the many forums about web hosting, ask the members for advice or search threads from those that have asked before you. Once you’ve located a few hosts to research, the ten questions below will take you a long way towards making an informed decision. You may be able to find many of the answers to these questions on the hosts’ web sites, but always feel free to call the host and quiz them about their operations. The quality of the answers and degree of professionalism you get from a potential host often transfers to the type of support you’ll receive once you become a customer. Without further ado, the ten question to ask your web host:

1. How long has the web host been in business?
2. Does the web host own its data center?
3. How many upstream Internet providers does the web host have?
4. Does the web host monitor its customers’ sites twenty-four hours per day? How?
5. Does the web host provide 24/7/365 phone and email support?
6. What levels of redundancy does the web host’s architecture provide?
7. Does the web host automatically backup customer web sites in case of data loss? How often?
8. What is the web host’s billing policy?
9. Does the web host provide the features that you need for your web site?
10. Does the web host have the products and services to handle your growth?

1. How long has the web host been in business?
The length of time that a host has been in business can be related to their ability to provide a quality, reliable product. If your host can satisfy its customers, then those customers are likely to stick with the host’s service. Therefore, stay in business. There are, of course, situations where this is not applicable or becomes a bit hazy. Be sure to also inquire about whether a host has recently been involved in a merger, acquired what was once a well-known brand name, or launched a new brand. If any of these apply, then delve deeper into the story behind what has happened and determine whether quality resources are still with the company.

• Complete a domain name “whois” lookup on the web host: http://www.internic.net/whois.html. Type in the web host’s domain name and determine what year the domain was registered. If only registered in the recent past, ask the host about it. If the domain name was recently registered this is not necessarily a red flag. Simply inquire with the host about it. They may have recently launched an affinity-based brand to cater to your market.
• Type the host’s name into a search engine and check out the results that you get, other than those from the host itself. You may run across reviews, interviews, or industry articles about the host.

2. Does the web host own its data center?
A data center is the foundation from which all products and services are built upon. If your host owns its own data center, then they are likely quite entrenched in the hosting business. They also have an experienced staff and knowledge base from which to draw from when supporting your web site and building new products. In other words, if a host owns its own facility, then it controls more of the variables that can make or break your web presence.

3. How many upstream Internet providers does the web host have?
Your web site performance is not just a measure of your web server’s speed. The ability of your web host to route traffic through the cleanest Internet connections is also of great importance. It is crucial that your provider have multiple connections to the Internet. Accidental fiber cuts in construction or telecom work and data center equipment failure can cause your site to go offline for an extended amount of time. This can be avoided if your web host has other connections to the Internet that will reroute traffic that would have normally been carried on the failed circuit. Yes, this means your host must also have extra capacity on hand to handle normal traffic levels when one connection is lost; which is another area where a host can attempt to cut cost. This is much like when driving your car, there are several streets that you can take to get to your desired destination. Sometimes you will encounter construction or an accident that will require you to take an alternative street. Well, the Internet works the same way. There are several routes that traffic can take to a destination. Your host should be able to choose the cleanest, or most efficient, route to your web site visitor. In fact, your host should be able to continually tune these routes to find the best path to your visitors. Another way to achieve this is by minimizing the number of different networks traffic will pass through before reaching its destination. It is extremely important for your host to have direct connections to networks that have lots of eyeballs. In other words, your web site will be served better if your web host is using connections with networks that facilitate Internet access to large volumes of subscribers.

4. Does the web host monitor its customers’ sites twenty-four hours per day? How?
There are a couple of factors that can influence the answer to this question. Does the host own its own data center? If not, then they are physically removed from their servers and likely paying a co-location company to provide monitoring for them. When another company controls the environmental systems that provide the home for the host, one can argue that you’ve created another potential point of failure; that being the communication of an issue from the data center to the web host. That point of failure can increase the latency between an issue and its resolution, resulting in increased downtime for your web site. Second, if your web host has an issue with its own infrastructure, then there may be travel time associated with their engineers getting to the data center to resolve it or, once again, increased latency by trying to remotely resolve an issue.